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.

Sign up for GitHub

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

Jump to bottom

control_origin needs to allow for multiple values #26

Closed
jbarnicle opened this issue Jun 30, 2016 · 3 comments
Closed

control_origin needs to allow for multiple values #26

jbarnicle opened this issue Jun 30, 2016 · 3 comments
Assignees
@jbarnicle
Labels
HighBar

Comments

@jbarnicle
Copy link
Contributor

jbarnicle commented Jun 30, 2016 •
edited by afeld
Loading

For some implementations (i.e. FedRamp), the control origination can contain multiple values.
@afeld
Copy link
Member

afeld commented Jul 1, 2016

Broken out from cloud-gov/cg-atlas#91 (comment).

@afeld afeld changed the title control_origination needs to allow for multiple values control_origin needs to allow for multiple values Jul 6, 2016
@mogul mogul added the HighBar label Jul 8, 2016
@pburkholder
Copy link
Contributor

Since control_origin is only about a month old, should we add control_origins as a seq and deprecate use of control_origin string as soon as feasible?

@afeld
Copy link
Member

afeld commented Jul 8, 2016

Sounds good to me! I'd advocate for the same approach here as #25.

@jbarnicle jbarnicle mentioned this issue Jul 19, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jbarnicle jbarnicle

Labels
HighBar
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mogul @afeld @jbarnicle @pburkholder @jcscottiii