I am trying to do a GET API call to get specific pipeline run history. The API URL is as follows
APIEndpoint/api/v3/namespaces/default/apps/DataPipeline_name/workflows/DataPipelineWorkflow/runs?limit=1
This API call needs a access token which I get by the command line
gcloud print-access-token
The above works fine on a Basic Edition
When I run this on enterprise edition instance, I get the following error
I need help here as to how I make this CDAP API call successfully.
Since the project of the Enterprise Edition of Cloud Data Fusion is different, you need to make sure that the account you logged in the gcloud has the correct permission to the Cloud Data Fusion instance. You need to grant the service account with the roles/datafusion.viewer.
You can read more about access control here
I'm not sure what caused the problem. But now it is working absolutely fine.
Maybe the permissions were an issue / there was something changed on the GCP Project.
Thanks for all your answers. Those make complete sense to check
Related
I am creating a JIRA plugin to fetch the issue-level permissions. Currently, the project-level permissions are working extremely fine but the issue-level permissions are not working. I tried finding a REST API to handle these permissions but, didn’t find anything so I decided to make a custom JIRA plugin to fetch the issue-level permissions of a project and handle them via exposing the plugin through an API.
My question is that what JIRA JAVA APIs do I have to use in order to handle these permissions? Or, is there any other workaround to handle issue-level permissions?
Maybe you are referring to the "Issue level security" term (??)
If so, you can get the issue security level name from the "security level" field attached to the issues (Use a Jira account that has an active "Set Issue Security" permission, in order to work with this system issue field). This can be done by REST API that queries issue fields.
Also, the JAVA API Interface is called: 'IssueSecuritySchemes' (at package: com.atlassian.jira.functest.framework.admin, for Jira Server/Data Center).
I am trying to integrate a project in Reportportal to JIRA project. When trying to configure, it is failing with error "Impossible interact with external system" like the attached picture.
The Jira service is up in docker. The https cert on JIRA is valid CA signed cert (i.e. Not self signed). I ruled out importing cert into jira service container.
The JIRA instance uses NTLM for authentication. I am not sure if Basic auth that reportportal jira service is trying working here.
Thanks for hep.
You should take a look into service-jira docker container logs. This will give details what's happening during this response.
and you also can drop as a mail to support#reportportal.io
Try This out !
You should take care of following points for reportportal.io integration with jira.
Link to BTS: This link should be correct.[https://jira.company.com]
Project name in Jira: Use project key instead of name. project key should taken from jira.
BTS username: Use jira email here.
BTS password: Use jira API token instead of password for Jira-cloud [Go to Jira account setting and generate new token or search how to generate jira API token]
All the best !
I already have a website running and want to install JIRA Server on it. So how do I add a sub directory to my main website, example www.mywebsite.com is my actual website so want www.mywebsite.com/Jira how do I achieve this?
I had downloaded the windows JIRA Installer and ran it locally connecting to the database hosted on my server and it worked using localhost(http://localhost:8080/secure/Dashboard.jspa) however now I want to access it through the web link i.e base URL.
I am new to this so any help would be really appreciated.
Well I understand you do have a domain and you want to run your JIRA with context path /jira un that domain. If that's the case, you may need to consider running your JIRA behind proxy. Take a look at Atlassian documentation since it contains all the information that you need for this:
https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html
I've been unsuccessful with having my build publish to the new Package Feed in TFS 15 RC2. I'm currently running TFS offline and using a local build agent. I've followed these instructions to no avail.
Since the last image in those instructions is cropped around the URL, and that URL was specific to VSTS online, I thought mine might be wrong. So I tried the following (none worked):
Using http://[computername]:8080/tfs/DefaultCollection/_packaging/{feedName}/nuget/v3/index.json
gives an error when it tries to prompt for input of credentials in
interactive mode.
Using http://[computername]:8080 gives a 404.
Using http://[computername]:8080/tfs gives same error as #1.
Using http://[computername]:8080/tfs/DefaultCollection gives same error as #1
Since some errors happened while trying to do an interactive prompt, I thought it might be a permission error. The following links give some information, but it seems like the Build Agent should already be in the right category for publishing permissions.
https://www.visualstudio.com/en-us/docs/package/feeds/common-identities
https://www.visualstudio.com/en-us/docs/package/nuget/auth
Anyone happen to know a solution? Thanks!
EDIT
The build agent was running as NT AUTHORITY/Network Service, which is the default of the agent config. I removed this agent and configured it to run under my user account, which is an admin on the system. After doing so, I was able to publish without issues to the Packages using the URL in #1 (as Cece below has written). Is there something else I need to do to get the permissions set for the default agent?
The Internal Feed URL is the NuGet Package Source URL for the feed you want to publish to.
When you create a new Feed, navigate to your feed, and select Connect to feed. You'll see the NuGet package source URL. The format should be like: http://{tfsserver}:8080/tfs/DefaultCollection/_packaging/{FeedName}/nuget/v3/index.json
I'm hosting a project on my Jenkins server. That project has a GitHub repo and I have it set up so it automatically builds new commits. In order for that to work, I need to input credentials for a github account that has full access to the repo.
The problem is, that if I want him to add his login info to the credentials list, I'd have to give him acces to all credentials on the server (I don't want that).
I tried using the credentials under "{username}" > "Credentials", but those didn't show up in the project setup (even with 100% access to everything on the server).
Is there a way for the user to store his credentials and use them for the project without giving him full access to all credentials on the server?
Add the user's credentials under Global security and then allow project based Matrix Authorization Strategy per project as shown:
I found the answer in this mailing list entry:
In short: You need to
install and activate the Authorize Projects Plugin,
enable "run as specific user" strategy in global security settings,
enable this for the project in question.
This allows you to use the credentials for this specific user.
Enabling ssh-agent is the final step to make this work conveniently.