vagrant credentials · Issue #8417 · koding/koding · GitHub
Skip to content
This repository was archived by the owner on Aug 15, 2022. It is now read-only.
This repository was archived by the owner on Aug 15, 2022. It is now read-only.

vagrant credentials #8417

Open
Open

Description

@rjeczalik

Currently we require user to paste kite ID to create vagrant credentials. If user creates stacks with that credentials, and then reinstalls kd - the stack would become unusable since new kd is going to have new kite ID.

The idea is to make it possible for a user to pick a managed VM from a list instead of typing kite ID and update kite ID if it changes (e.g. due to reinstall).

/cc @leeola

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Activity

  1. gokmen commented on Jul 13, 2016

    @gokmen
    Contributor

    So, user will require to choose the machine from the ui on each operation? If kiteId is changed?

  2. leeola commented on Jul 13, 2016

    @leeola
    Contributor

    Could there be any issue if the user chooses the wrong machine?

    Lee

    On Wed, Jul 13, 2016 at 10:55 AM, Gokmen Goksel notifications@github.com
    wrote:

    So, user will require to choose the machine from the ui on each operation?
    If kiteId is changed?

    —
    You are receiving this because you were mentioned.
    Reply to this email directly, view it on GitHub
    #8417 (comment), or mute
    the thread
    https://github.com/notifications/unsubscribe/AAC5xJwQ7yBvsict_rOTQ6-nTowemBN5ks5qVSajgaJpZM4JLrYU
    .

  3. rjeczalik commented on Jul 13, 2016

    @rjeczalik
    ContributorAuthor

    Not sure about the perfect flow - I think it should be something like:

    1. a vagrant vm is turned off
    2. user reinstalls kd
    3. vm start fails due to old kite id not valid any longer (jMachines.credential)
    4. we allow somehow for updating jMachines.credential without reinitializing (destroying) stack

    Makes sense?

  4. assigned and unassigned on Feb 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions