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

[CI/CD] Export Environment Variables About Resources #150

Open
samyfodil opened this issue May 8, 2024 · 0 comments
Open

[CI/CD] Export Environment Variables About Resources #150

samyfodil opened this issue May 8, 2024 · 0 comments
Labels
advanced feature New feature or request urgent Urgent task

Comments

@samyfodil
Copy link
Contributor

Currently, when a repository is built, it is assumed to be agnostic of where and how it will be run. For instance, if I want to use the same website repository for two different domains, or a domain and a sub-folder, I would need to merge a submodule into the repository and add something like a GitHub Action that automatically updates the submodule. This issue can be easily solved by adding context to CI/CD runs.

The idea is to simply export an environment variable and a filesystem (folder) with the configuration, or at least a subset of it.

Exporting the configuration repository may pose a question: Should we clone the current branch, or should we clone the current commit on the branch? Upon reflection, using the current commit should be the preferred method, as it will cause the build to fail and retry if the node is not up-to-date yet. Another method could be to decompile and generate the configuration from TNS.

@samyfodil samyfodil added feature New feature or request advanced urgent Urgent task labels May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
advanced feature New feature or request urgent Urgent task
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant