-
Notifications
You must be signed in to change notification settings - Fork 33
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
Enhancement: Docker Swarm stack name added. #26
base: development
Are you sure you want to change the base?
Enhancement: Docker Swarm stack name added. #26
Conversation
@linl33 |
@linl33 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 small issues but otherwise the script works.
I noticed that your commit was based off of the master branch. There are changes in the development branch that are useful for testing.
@@ -97,8 +105,7 @@ def run_interactive_config(): | |||
--non-interactive".format(email, domain)) | |||
|
|||
print("Attempting to save updated https configuration") | |||
write_to_env_file(env_file_location, domain, email) | |||
|
|||
write_to_env_file(env_file_location, domain, email, stack_name) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should not be guarded behind enforce_https
anymore.
@@ -19,7 +19,7 @@ def run_interactive_config(): | |||
env_file_location = os.path.join(os.path.dirname(__file__), "config", "https.env") | |||
|
|||
try: | |||
domain, email = parse_env_file(env_file_location) | |||
domain, email, stack_name = parse_env_file(env_file_location) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For a user coming from a previous version, stack_name
would be None
here. Please add a check.
This looks fine to me 👍 |
(oops - sorry I fumbled - didn't mean to close it.) |
@adityaofficial10 please take a look at the PR feedback and possibly make the requested changes to address the issues. You can push additional commits to the same branch and it will automatically add it to the PR. |
@wbrunette |
@adityaofficial10 no worries. We are trying to provide more directions for GSoC/Outreachy since it may be someone's first time involved in open-source projects. |
@wbrunette |
@adityaofficial10 Could you give us an update on this pull request? Let us know if you're having any difficulties or questions. |
@linl33 |
@wbrunette I'm still waiting on changes requested in the previous review. |
@adityaofficial10 can you give us an update on your progress? Do you have any questions? |
@adityaofficial10 can you give us an update on your progress? Do you have any questions? |
@wbrunette @linl33 |
Hello team, I'm an Outreachy applicant for the winter 2023 season and have been assigned issue: issue: https://github.com/odk-x/tool-suite-X/issues/194 Regards, |
@MariaAngella you should start fresh with your own branch and learn about Git. |
@wbrunette will work from my branch thanks. Regards, |
@wbrunette , kindly advise if I'm on the right track my branch Thank you and regards, |
Fixes issue: odk-x/tool-suite-X#194
What changes have been made?