Closed endzyme closed 5 years ago
How to test this
Existing AWS functionality
pentagon add inventory \
-Dcloud=aws \
-Dinfrastructure_bucket=asdf \
-Dname=somename \
-Daws_access_key=fake \
-Daws_secret_key=fake \
-Dproject_name=fakeproject \
-o output_path
Testing with gcp settings
pentagon add inventory \
-Dcloud=gcp \
-Dcluster_name=mycluster \
-Dkubernetes_version=1.11.7-gke6 \
-Dnodes_cidr=1.2.3.0/24 \
-Dpods_cidr=2.3.4.0/24 \
-Dservices_cidr=3.4.5.0/24 \
-Dproject=fake-project-one \
-Dinfrastructure_bucket=asdf \
-Dname=somename \
-Dproject_name=fakeproject \
-o output_path_gcp
Testing gcp cluster without generating an inventory
pentagon add gcp.cluster.public \
-Dcloud=gcp \
-Dcluster_name=mycluster \
-Dkubernetes_version=1.11.7-gke6 \
-Dnodes_cidr=1.2.3.0/24 \
-Dpods_cidr=2.3.4.0/24 \
-Dservices_cidr=3.4.5.0/24 \
-Dproject=fake-project-one \
-o only_the_tf_cluster_path
Things I don't like
-Dvarname=xyz
due to how the data for each class invocation is handed down (not addressable in this PR)project
vs project_name
is one of these examples: gcp project vs wherever project-name is used)NOTE: I still haven't tested if the terraform runs
Latest push fixes the pentagon start-project proj-name
issue (it didn't run before).
Now you can run:
pentagon debug start-project testing \
--cloud gcp \
--gcp-project testing-gcp-project \
--gcp-cluster-name cluster-name-1 \
--gcp-pods-cidr 0.0.0.0/1 \
--gcp-nodes-cidr 0.0.0.0/1 \
--gcp-services-cidr 0.0.0.0/1
@ejether I added some different mechanism for versioning here - can you review again (specifically on integrating versioneer)
@ejether I added some different mechanism for versioning here - can you review again (specifically on integrating versioneer)
Ignore this @ejether - it broke more than it solved. I will update the changelog and some other normal versioning procedures
add inventory