-
Notifications
You must be signed in to change notification settings - Fork 7
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
Offer only valid team_ids #454
Labels
Comments
👍 * 1000 There is also an API for teams we use anyways. However the reason for showing accounts instead of teams was that back in the days freelancers then couldn't e.g. push docker images to the team's namespace because they were organizationally not part of the team. Before implementing this we have to double-check what it means for our services. |
prayerslayer
added a commit
that referenced
this issue
Jun 16, 2016
prayerslayer
added a commit
that referenced
this issue
Jun 16, 2016
prayerslayer
added a commit
that referenced
this issue
Jun 16, 2016
prayerslayer
added a commit
that referenced
this issue
Jun 16, 2016
prayerslayer
added a commit
that referenced
this issue
Jun 16, 2016
prayerslayer
added a commit
that referenced
this issue
Jun 16, 2016
prayerslayer
added a commit
that referenced
this issue
Jun 16, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current team_id-selectbox options within application/edit form, offer AWS account ids instead of team ids. However if one selects a team, that is not recognized by the teams API, the process of creating service users for the application will fail.
Please offer only valid team ids. Hint: The "owner" of the aws accounts could be used as possible options.
The text was updated successfully, but these errors were encountered: