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

Make provisioning and releasing more explicit #204

Open
rtholmes opened this issue Jan 7, 2019 · 1 comment
Open

Make provisioning and releasing more explicit #204

rtholmes opened this issue Jan 7, 2019 · 1 comment
Assignees
Labels
portal-backend wontfix This will not be worked on
Milestone

Comments

@rtholmes
Copy link
Contributor

rtholmes commented Jan 7, 2019

Add explicit fields to Repository to track provisioning and releasing. I propose:

Repository.provisioned : boolean to just track whether it has been provisioned. We use URL for this right now, but it is indirect (aka if URL === null then it is not provisioned).

Repository.released: Status should also be used. Status is just to give us more flexibility, for now I propose NotReleased | ReadOnly | ReadWrite.

Also need to remove Team::custom::githubAttached and `Repossitory::custom::githubProvisioned```.

@rtholmes rtholmes added this to the v3.0 milestone Jan 7, 2019
@rtholmes rtholmes self-assigned this Jan 7, 2019
rtholmes added a commit that referenced this issue Jan 8, 2019
rtholmes added a commit that referenced this issue Jan 8, 2019
@rtholmes rtholmes added the wontfix This will not be worked on label Jan 13, 2020
@rtholmes
Copy link
Contributor Author

Updated label for now; we can come back to this if we need to, but this won't be a high priority unless something changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
portal-backend wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant