Artifactory Permission management for specific group members - artifactory

In our current Artifactory setup we have created Repos, groups and permissions per application like below
Example: For Application app-A1, we have created 2 repos(local-A1 and virtual-A1) , 2 groups(appA1-developers, appA1-contributors) and a permission target (appA1-permission) where we will include the created 2 repos and groups with the permissions.
similarly, For Application app-A2, we have created 2 repos(local-A2 and virtual-A2) , 2 groups(appA2-developers, appA2-contributors) and a permission target (appA2-permission) where we will include the created 2 repos and groups with the permissions.
So as explained the above setup is done on Application specific, But now we have to group these existing applications under portfolios level (say multiple App repos under 1 portfolio , in the above example, PortfolioA will hold Apps A1 and A2), There we have to Assign certain dedicated members to manage the permission on their Sub App Repos.
How we can achieve this is in Artifactory?
We tried to use the Project Concept here, but since we have many Portfolios (almost 100), we cant create project for each portfolios.

Related

How to use AWS profile with Amplify?

Amplify does not support CLI option --profile. It always uses profile specified when application was generated. Different team members use different AWS profiles.
How to change/configure/use profile different than profile used during application generation?
Aim is to publish changes from different computer. Final goal is to use CI server to publish application to different regions.
Amplify does not work like "other" development tools where tool is detached from git. Amplify goes hand in hand with Git and requires initialization after cloning. Running amplify init and choosing existing environment (which is pushed by other developer), it is possible to select different AWS profile.

How to Read data from 2 different Firebase database which are from 2 different projects

Basically i want to access two different databases form two different projects in firebase from one flutter app,
For more info ,
I have build a single Flutter app in which ,
some time i want to refer to one database of (Project name "A" ) and some time i need to refer another database of (Project name "B") ,
is there a way to refer to 2 different database at a time in single app.
Thanks in advance.
Yes, it is possible to read data from 2 different Firebase databases through a single app. Simply go to your Home page on your Firebase console and app your app (both iOS and Android, I assume, since you are developing with Flutter) for both databases.

Octopusdeploy deploy multiple sites from one package

I have a unique situation where I have a package created by TeamCity which contains two sites. For e.g. package-1.0.zip contains Site1 and Site2 in it.
How can I deploy these two sites using octopus deploy? Both sites have their own application pool, config transformation, etc..
Is there any way, I can reference those two folders inside the package when creating IIS site deployment steps so that I can create two steps to deploy those two different sites?
Thanks
I think you can achieve this by having two "Deploy to IIS" steps in your Process and changing the Physical Path setting to "Relative path under package installation directory"
This should allow you to configure each site with different IIS settings while still using the same package.
Edit: based on your comments, this process may work for you
Use the Deploy a Package step to deploy the package contents to the target machine.
Enable custom deployment scripts (click "Configure Features" next to the Save button on the step details and then select "Custom deployment scripts").
Write a custom deployment script to copy Site1 and Site2 to the appropriate folders.
If you need to configure IIS after that step (site, app pool, etc) there are many Community Step templates for those actions. Search for IIS to see the full listing.
We do a similar deployment, Where octopus receives the package containing multiple sites.
We break it into different packages, unzipping and zipping the package and using octopkg push as a seperate library and deploy them as different sites, using custom install directories.

How to merge 2 gcp project

I have 2 different gpc project, one with all my running servers, and another running my firebase app is there a way to merge those 2 ?
At present there is no GCP options to merge projects, however I have created a feature request to provide this functionality in the future. There is not ETA but any progress on it can be followed at the above link.
As a workaround you can create VM disk snapshots images of your VM instances from one project and move them incrementally to the other. Once you are completely sure that the migrated VMs are working properly in the destination project, you can shut down the other project which you can still restore within 30 days in case you may need to do so.
I am not familiar with Firebase so you would have to take into account any issues with DNS resolution and domain issues with your application if you decide to move the app in that project instead.

Create Content Selector and Privileges via script for separating a docker registry into project owned namespaces

Do you know if there is any way to create content selectors and content selector privileges via script for Nexus Repository Manager OSS?
Thanks in advance for every answer :-)
My idea is to divide a hosted Docker Repository into separated (protected) namespaces (for each product/team/project) - I do not want to do the following steps manually; a better approach is to create a script for that:
1 Create Content Selector
format == "docker" && (path == "/v2/" || path =^ "/v2/PROJECTNAME/")
2 Create Content Selector Privilege
Use the selector created in step 1 and choose a docker repo.
3 Create role
Create a role and grant the privilege created in step 2
4 Create user
Create a user with a randomly generated pwd and grant the role from step 3 to newly created user.
A project can use this user to access the docker registry only within its granted Namespace
This gist should provide enough detail to get you rolling:
https://gist.github.com/nblair/1a0e05713c3edb7e5360c2b0222c7623
Hope this helps!

Resources