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.

Sign up for GitHub

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

Jump to bottom

Support defining separate default configs for each organization #39

Closed
eclipse-csi-bot opened this issue May 15, 2023 · 2 comments
Closed

Support defining separate default configs for each organization #39

eclipse-csi-bot opened this issue May 15, 2023 · 2 comments

Comments

@eclipse-csi-bot
Copy link
Contributor

In GitLab by @netomi on May 15, 2023, 11:15

We need to improve the way we specify and track the currently used default configuration of an org.
Currently there is only one setting in the otterdog.json that refers to the default config being used, but this is shared by all orgs.
We might have different defaults for some orgs, or they use different tags for the default config coming from the same repo.
@eclipse-csi-bot
Copy link
Contributor Author

In GitLab by @netomi on Jun 12, 2023, 16:31

mentioned in commit 38b92e4

@eclipse-csi-bot
Copy link
Contributor Author

In GitLab by @netomi on Jun 12, 2023, 16:33

Implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eclipse-csi-bot