Jira (PUP-10306) Environments should track their version

0 views
Skip to first unread message

Maggie Dreyer (JIRA)

unread,
Feb 20, 2020, 6:14:06 PM2/20/20
to puppe...@googlegroups.com
Maggie Dreyer created an issue
 
Puppet / Task PUP-10306
Environments should track their version
Issue Type: Task Task
Assignee: Unassigned
Created: 2020/02/20 3:13 PM
Priority: Normal Normal
Reporter: Maggie Dreyer

Currently, an environment is initialized with its name and module path. When we move to using versioned environments, the environment object should also store the version of the env at the time it was created.

We are planning to have file-sync put this version in a JSON metadata file in the environment directory (probably the same file as in CODEMGMT-1238). Since environments do not store their own paths, the caller of Environment.create most likely needs to load this and pass it along to the created environment.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Maggie Dreyer (JIRA)

unread,
Feb 20, 2020, 6:39:05 PM2/20/20
to puppe...@googlegroups.com
Maggie Dreyer updated an issue
Change By: Maggie Dreyer
Currently, an environment is initialized with its name and module path. When we move to using versioned environments, the environment object should also store the version of the env at the time it was created.

We are planning to have file-sync put this version in a JSON metadata file in the environment directory (probably the same file as in CODEMGMT-1238). Since environments do not store their own paths, the caller of {{Environment.create}} most likely needs to load this and pass it along to the created environment.

Molly Waggett (JIRA)

unread,
Feb 24, 2020, 4:56:03 PM2/24/20
to puppe...@googlegroups.com
Molly Waggett assigned an issue to Molly Waggett
Change By: Molly Waggett
Assignee: Molly Waggett

Molly Waggett (JIRA)

unread,
Feb 24, 2020, 5:21:03 PM2/24/20
to puppe...@googlegroups.com
Molly Waggett updated an issue
Currently, an environment is initialized with its name and module path. When we move to using versioned environments, the environment object should also store the version of the env at the time it was created.

We are planning to have file-sync put this version in a JSON metadata file in the environment directory (probably the same file as in CODEMGMT-1238). Since environments do not store their own paths, the caller callers of {{Environment.create}} most likely needs need to load this and pass it along to the created environment.

Molly Waggett (JIRA)

unread,
Feb 25, 2020, 1:10:07 PM2/25/20
to puppe...@googlegroups.com
Molly Waggett commented on Task PUP-10306
 
Re: Environments should track their version

Because we hold onto the same environment object throughout the lifecycle of a compile, we don't actually need to hold onto the environment version, since we already have the environment we need. Closing this.

Maggie Dreyer (JIRA)

unread,
Feb 25, 2020, 1:41:04 PM2/25/20
to puppe...@googlegroups.com

Since we're going to need this if we do any of the follow-on work like PUP-10306, I'm gonna just throw this back in the backlog for now. It'll probably become part of a separate epic at some point.

Molly Waggett (Jira)

unread,
Apr 17, 2020, 12:15:03 AM4/17/20
to puppe...@googlegroups.com
Molly Waggett assigned an issue to Unassigned
 
Change By: Molly Waggett
Assignee: Molly Waggett
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Nick Walker (Jira)

unread,
May 22, 2020, 2:02:04 PM5/22/20
to puppe...@googlegroups.com
Nick Walker updated an issue
Change By: Nick Walker
Epic Link: PE CODEMGMT - 26632 1270

Maggie Dreyer (Jira)

unread,
Feb 5, 2021, 11:27:04 AM2/5/21
to puppe...@googlegroups.com
Maggie Dreyer updated an issue
Change By: Maggie Dreyer
Epic Link: CODEMGMT- 1270 1382
Reply all
Reply to author
Forward
0 new messages