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

Drop support for schema_v3 #243

Closed
samvarankashyap opened this issue May 23, 2017 · 2 comments
Closed

Drop support for schema_v3 #243

samvarankashyap opened this issue May 23, 2017 · 2 comments
Milestone

Comments

@samvarankashyap
Copy link
Collaborator

samvarankashyap commented May 23, 2017

From recent discussions PR #236 . Its agreed upon to drop the support for schema_v3 from 1.1.0 release.
Note:
However, schema_v3 continuous to work with the resource_group_types except openstack, aws, gcloud due to recent changes in authentication mechanism using auth_driver PR #236 .
Further , all the other playbooks for provisioning are to be updated in accordance with how authdriver parses files from --creds-path ref #76
Moreover, It's also to be noted that eventually the way linchpin handles schema will be subjected to change w.r.to PR #235 in near future releases removing all the references to schemas.

@samvarankashyap samvarankashyap added this to the v1.1.0 milestone May 23, 2017
@herlo herlo modified the milestones: v1.2, v1.1 Jun 14, 2017
@herlo herlo added this to To Be Groomed (New) in LinchPin 1.0.x Jun 14, 2017
@herlo
Copy link
Contributor

herlo commented Jun 22, 2017

Reworking Schema

@herlo herlo removed this from To Be Groomed (New) in LinchPin 1.0.x Sep 6, 2017
@herlo herlo modified the milestones: v1.5, v1.1 Sep 6, 2017
@herlo herlo added this to New (Ungroomed) in LinchPin 1.5 Sep 14, 2017
@herlo
Copy link
Contributor

herlo commented Dec 24, 2017

release of linchpin v1.5.0rc1 no longer uses schema_v3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
LinchPin 1.5
New (Ungroomed)
Development

No branches or pull requests

2 participants