-
Notifications
You must be signed in to change notification settings - Fork 48
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
Update Project to Use Poetry #68
Conversation
…ment. To replace use of requirements.txt we'll use pyproject.toml with Poetry.
…nvironments folder.
What is the part about adding invoke onto this? Are we still able to do |
I still need to finish updating documentation to include that bit. I think you should still be able to do 'docker compose up' in the environments folder if you specify the project or which files. Need to test to confirm though. |
I've confirmed that you are able to use |
Cleaned up optional settings and RQ related settings that are no longer valid.
|
||
``` | ||
docker compose -f docker-compose.yml -f docker-compose.mysql.yml up | ||
This repo is designed to provide a custom build of Nautobot to include a set of plugins which can then be used in a development environment or deployed in production. Included in this repo is a skeleton Nautobot plugin which is designed only to provide a quick example of how a plugin could be developed. Plugins should ultimately be built as packages, published to a PyPI style repository and added to the poetry `pyproject.toml` in this repo. The plugin code should be hosted in their own repositories with their own CI pipelines and not included here. |
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 seems wrong? We're not going to add any plugins to this repo's pyproject.toml
? If the idea is for users to maintain a custom fork with their own set of plugins, that should be made clearer.
(Also, nit - s/plugin/app/g
:-) )
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.
The example plugin was included as there is one in the current version. I think it might be worthwhile to just get rid of it and refer to the cookiecutter-nautobot-app cookies instead. Thoughts? @jvanderaa @glennmatthews
healthcheck: | ||
test: ["CMD", "true"] # Due to layering, disable: true won't work. Instead, change the test |
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.
remove?
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.
I think we should probably come up with a good healthcheck like for the nautobot service.
MYSQL_USER=nautobot | ||
MYSQL_DATABASE=nautobot |
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.
I don't understand the logical split between creds.example.env
and local.example.env
- for example, why is MYSQL_USER
in local
but MYSQL_PASSWORD
in creds
?
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.
I considered local.env to be environment variables that are safe to be stored in git vs secrets that shouldn't be saved should go into creds.env.
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.
So a user would fork the repo and commit local.env
to their fork? Maybe document that if so.
compose_dir: "environments/" | ||
compose_files: | ||
- "docker-compose.postgres.yml" | ||
- "docker-compose.ldap.yml" |
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.
Why does the ldap
one not include docker-compose.base.yml
?
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.
Because the LDAP compose file is identical to base but uses the LDAP Dockerfile. I guess we could just use overrides in this case but was trying to make it easier to understand.
…nd caching_sha2_password
This PR is to refactor the project to use Poetry for dependency management instead of requirements.txt and the older build system. I've made this update to address the following: