Skip to content

fix: fix keypair handling in e2e scrip #199

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

Merged
merged 1 commit into from
Nov 19, 2025
Merged

fix: fix keypair handling in e2e scrip #199

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions test/e2e/e2e.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ log_success() {
}

log_warn() {
printf "[$(date +'%T')] ⚠️ %s\n" "$*" >&2
printf "[$(date +'%T')] ⚠️ %s\n" "$*" >&2
}

log_error() {
Expand Down Expand Up @@ -191,10 +191,10 @@ update_inventory() {
setup_ssh_key() {
log "Checking for SSH key '$SSH_KEY_NAME'..."

if ! stackit key-pair describe "$SSH_KEY_NAME" --project-id "$PROJECT_ID" &>/dev/null; then
if ! stackit key-pair describe --public-key "$SSH_KEY_NAME" --project-id "$PROJECT_ID" &>/dev/null; then
log "No existing key found. Creating..."
# The '@' prefix tells the CLI to read the content from the file
if ! stackit key-pair create --public-key "$SSH_KEY_NAME" -y \
if ! stackit key-pair create --name "$SSH_KEY_NAME" -y \
--project-id "$PROJECT_ID" \
--public-key "@$HOME/.ssh/$SSH_KEY_NAME.pub"; then
log_error "Failed to create SSH key '$SSH_KEY_NAME' in STACKIT."
Expand Down