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

Kanalstøtte #1068

Closed
Remi749 opened this issue Mar 29, 2023 Discussed in #789 · 1 comment · Fixed by #1047
Closed

Kanalstøtte #1068

Remi749 opened this issue Mar 29, 2023 Discussed in #789 · 1 comment · Fixed by #1047
Assignees
Labels
ci Related to Continuous Integration (GitHub Workflows/Actions) complexity: large Issue/PR with large complexity customer funded Issues funded by customer enhancement Request that will enhance the product
Milestone

Comments

@Remi749
Copy link
Collaborator

Remi749 commented Mar 29, 2023

Discussed in #789

Originally posted by pzljanb April 6, 2022
Is your feature request related to a problem? Please describe.
Users are not able to install a new release of PP365 to test it in an existing environment in a good way.
Resources in the AppCatalog is shared between installations within the same tenant and does not support multiple versions to be installed.

Describe the solution you'd like
PP365 solution to be released in different channels (dev, beta, prod e.g.)
For this to work it's necessary to separate the resources used within the solution to make sure it does not interfere with different versions/ channels.

Resources affected:

  • Webparts e.g. in the AppCatalog

These must be duplicated

  • Termstore elments

These could be considered to be kept common in the first iteration

There is 2 different solutions (at least?) that could be considered to make this happen:

1. Call to resources in AppCatalog to be made based on the installations current channel ID

To get this to work the code must check which channel it is on and call the ID based on this
The code keeps info on all different AppCatalog IDs in this scenario

2. Swop reference to AppCatalog resources in the code when moving to the next channel (preferred?)

For this solution to work the ID used to call AppCatalog resources must be replaced thru the codebase each time the code goes to the next channel.

Additional context
A solution like this would make user organizations of PP365 able to install and test the next release before upgrade PROD environment.

Is this something your organization is willing to contribute to financially?

@Remi749 Remi749 added enhancement Request that will enhance the product complexity: large Issue/PR with large complexity customer funded Issues funded by customer ci Related to Continuous Integration (GitHub Workflows/Actions) labels Mar 29, 2023
@Remi749 Remi749 added this to the 1.9 milestone Mar 29, 2023
@olemp olemp linked a pull request Mar 29, 2023 that will close this issue
4 tasks
@olemp
Copy link
Collaborator

olemp commented Mar 31, 2023

@olemp olemp closed this as completed Mar 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Related to Continuous Integration (GitHub Workflows/Actions) complexity: large Issue/PR with large complexity customer funded Issues funded by customer enhancement Request that will enhance the product
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants