Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cleanup (Admin-dash) #1 - Tasks: A-2, 6, 7, 8 #132

Closed
wants to merge 5 commits into from

Conversation

MukuFlash03
Copy link
Contributor

@MukuFlash03 MukuFlash03 commented Sep 23, 2024

First set of cleanup changes for the redesign cleanup issue

Includes changes for tasks:
Task A-2: Reading tags from .env files instead of uploading artifacts.
Task A-6: Switch to GITHUB_OUTPUT step outputs instead of using GITHUB_ENV.
Task A-7: Certificates moved to internal Dockerfiles.
Task A-8: Tags now stored as <branch_name>_<timestamp>


Note: Once these changes are merged, the internal PR with the updates to the internal script must also be merged since no longer uploading artifacts externally, hence internal script must also be updated to fetch tags from .env files instead.

Mahadik, Mukul Chandrakant added 4 commits September 20, 2024 22:23
Refer to details in cleanup issue:
Task A-2: e-mission/e-mission-docs#1082 (comment)

Added .env file initialized with the current latest tag of admin-dash and server image.
Internal script can read docker image tags directly from .env.tags using curl to fetch raw file contents.
Storing server tag as well since admin-dash Dockerfile uses it.

Removed workflow dispatch inputs
No longer need inputs since reading from .env.tags in server repo directly

------

Read raw file contents directly instead of using REST API
REST API endpoint returns base64 encoded data which then needs to be decoded.
Can simply read the Raw file contents from the publicly available file.

-----

For now not removing artifacts until the internal script is updated to handle this change.
…ternal

Task A-8: Prefixing branch name to the docker tag along with the date.
In the internal script we will not need to maintain the different branch lists as the images will be completely tagged in the external workflows themselves.
We can simply use the tags without modifications then.

For now, not prefixing the tag to the artifact since we will be removing the artifact anyways.
And current internal script works with artifacts.
Once I update the internal script, will come back and remove artifacts.

In Dockerfile, removing hardcoded branch name, since in this change, we are already included the branch name in image tag.

----------

Task A-7: Certifcates added to internal Dockerfiles.

Refer to issue comment for details:
Task A-7: e-mission/e-mission-docs#1082 (comment)

The certificates are relevant to our internal AWS configuration and not needed externally.
They can be present externally too without having any major effect.
But removing them helps keeping the base image clean.
Additionally, anyone working with the code can customize with their own certificates if needed or adopt an approach which doesn't even need certificates in the first place.
Internal script updated as well.
Internal PR must be merged as well once these external PR changes merged.
@shankari shankari deleted the branch e-mission:master-old October 21, 2024 20:42
@shankari shankari closed this Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Tasks completed
Development

Successfully merging this pull request may close these issues.

2 participants