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

airshipctl document pull has a default pull from treasuremap that is not documented #416

Closed
bravinash82 opened this issue Nov 18, 2020 · 8 comments
Assignees
Labels
5-Documentation Improvements or additions to documentation bug Something isn't working priority/critical Items critical to be implemented, usually by the next release ready for review Change related to the issue is ready for review size m
Milestone

Comments

@bravinash82
Copy link
Contributor

Describe the bug
when "airshipctl document pull" is executed. Airshipctl automatically pulls/clones a default repository from treasuremap.

Steps To Reproduce
Execute "airshipctl document pull".

Expected behavior
Neither "https://docs.airshipit.org/airshipctl/cli/airshipctl_document_pull.html" nor the "airshipctl document pull --help" actually documents the fact that it does an automatic pull from treasumemap. Also should provide a mechanism to pull from non-default custom repository as well..

Environment

  • airshipctl Version: v0.1.0 (from Master)
  • Operating System: Ubuntu 20.04 LTS
  • Kernel version: 5.4.0-48-generic
  • Kubernetes Version: N/A
  • Go version: go1.15.2 linux/amd64
  • Hardware specs (e.g. 4 vCPUs, 16GB RAM, bare metal vs VM): VM (4 vCPU), 8GB RAM, 60GB HDD
@bravinash82 bravinash82 added bug Something isn't working triage Needs evaluation by project members labels Nov 18, 2020
@kozhukalov
Copy link
Contributor

please, assign it to me

@jezogwza jezogwza added 5-Documentation Improvements or additions to documentation priority/critical Items critical to be implemented, usually by the next release and removed triage Needs evaluation by project members labels Dec 9, 2020
@jezogwza jezogwza added this to the v2.0 milestone Dec 9, 2020
@sb1975
Copy link
Contributor

sb1975 commented Dec 9, 2020

Hope this helps - the url can be specified in the variable below :
: ${TREASUREMAP_PROJECT:="$(pwd)"}
which is referred below :
export AIRSHIP_CONFIG_PRIMARY_REPO_URL=${AIRSHIP_CONFIG_PRIMARY_REPO_URL:-"${TREASUREMAP_PROJECT}"}

https://github.com/airshipit/treasuremap/blob/v2/tools/deployment/22_test_configs.sh#L18

@kozhukalov
Copy link
Contributor

@kozhukalov
Copy link
Contributor

@bravinash82 could you please review the patch? Does it solve the issue?

@lb4368 lb4368 added the ready for review Change related to the issue is ready for review label Mar 26, 2021
@michaelfix
Copy link

@kozhukalov , @bravinash82 , what is the latest status? PS https://review.opendev.org/c/airship/airshipctl/+/767571 is pending core reviews and workflow. Needed for V2.0 which closes 3/30?

@lb4368
Copy link

lb4368 commented Mar 30, 2021

This issue is dependent upon final design for #417.

@lb4368 lb4368 modified the milestones: v2.0, v2.1 Mar 30, 2021
@airshipbot
Copy link

airshipbot commented Apr 20, 2021

Related Change #767571

Subject: Change default manifest target path
Link: https://review.opendev.org/c/airship/airshipctl/+/767571
Status: MERGED
Owner: Vladimir Kozhukalov ([email protected])

Approvals

Code-Review
+2 Matt McEuen
+2 Kostyantyn Kalynovskyi
Verified
+1 ATT Airship2.0 CI
+2 Zuul
Workflow
+1 Kostyantyn Kalynovskyi

Last Updated: 2021-05-06 16:59:09 CDT

airshipbot pushed a commit that referenced this issue May 6, 2021
  Now the target path for the default manifest is
  $HOME/.airship/default. This is reasonable default
  location.

  The target path is a mandatory field in the
  definition of a manifest. If a user wants
  to use her current working directory as a location
  the manifests, then it must be properly configured
  in the $HOME/.airship/config.

Relates-To: #416
Relates-To: #417
Change-Id: I96601803939df5c7369d1580842dfabeb19aa017
@eak13
Copy link

eak13 commented Jun 28, 2021

Closing per patchset merge

@eak13 eak13 closed this as completed Jun 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5-Documentation Improvements or additions to documentation bug Something isn't working priority/critical Items critical to be implemented, usually by the next release ready for review Change related to the issue is ready for review size m
Projects
None yet
Development

No branches or pull requests

9 participants