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

Deprecate old flags #2992

Closed
1 task
nitrocode opened this issue Jan 17, 2023 · 6 comments · Fixed by #4047
Closed
1 task

Deprecate old flags #2992

nitrocode opened this issue Jan 17, 2023 · 6 comments · Fixed by #4047
Labels
feature New functionality/enhancement
Milestone

Comments

@nitrocode
Copy link
Member

nitrocode commented Jan 17, 2023

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Describe the user story

For 1.0 release, we want to remove the old flags (and respective environment variable) from the code in favor of their respective newer approaches documented below

See issue #2496

Describe the solution you'd like

Remove old flags from the code
Remove old flags from the docs

Describe the drawbacks of your solution

None

Describe alternatives you've considered

None

@nitrocode nitrocode added the feature New functionality/enhancement label Jan 17, 2023
@nitrocode nitrocode added this to the v1.0.0 milestone Jan 31, 2023
@DragosDumitrache
Copy link

Can I check, is it just the flag that's deprecated? Particularly interested in --require-mergeable. Could I still enable that via the environment variable?

@nitrocode
Copy link
Member Author

nitrocode commented Feb 1, 2023

It would be both the flag and its environment variable. Instead of require-mergeable, you'd have to use the non-deprecated method after this ticket is completed to keep the same functionality.

@DragosDumitrache
Copy link

I see, thanks for getting back to me so quickly. And I assume, much like the server side config file, the repo config is sourced from the current branch of the repo as well, right?

@nitrocode
Copy link
Member Author

@DragosDumitrache the repo config is server side

@DragosDumitrache
Copy link

Oh, so, changing it on a branch won't affect the configuration unless a new atlantis is deployed?

@nitrocode
Copy link
Member Author

it's a server side configuration so atlantis will have to be restarted / redeloyed when the change is made

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New functionality/enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants