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

Develop github actions to deploy api to different environments #111

Closed
sujen1412 opened this issue Apr 17, 2024 · 1 comment · Fixed by #121, #123 or #113
Closed

Develop github actions to deploy api to different environments #111

sujen1412 opened this issue Apr 17, 2024 · 1 comment · Fixed by #121, #123 or #113
Assignees

Comments

@sujen1412
Copy link
Collaborator

No description provided.

@frankinspace
Copy link
Contributor

API is now being deployed to DIT environment via GH Action.

API settings are consolidated into a single environment secret called MAAP_API_SETTINGS_OVERRIDE. Follow on ticket will address this #124

Every push to the develop branch will trigger an automated deployment to DIT. Recent deployments can be monitored at https://github.com/MAAP-Project/maap-api-nasa/deployments

Every push to the develop branch will tag a new 'alpha' release. Alpha number is incremented by 1 on every push. The alpha version will be used as the docker tag for the image in addition to an environment-specific tag (DIT in this case). Docker images and tags can be viewed at https://github.com/MAAP-Project/maap-api-nasa/pkgs/container/maap-api-nasa. Docker images are also pushed to GitLab, discussion to remove this is tracked in #125

Deployments are achieved by using an organization level self-hosted runner which is running in the deployment environment. docker-compose is used to restart the service. It would be preferable to deploy via terraform without a need for self-hosted runner. This is tracked in #126

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment