I'm creating a separate app for users to visualize GitLab issues without needing access to GitLab. We are using python-gitlab to retrieve the issue data for display on this separate site. Users will create new issues by clicking a button that opens up an email configured with the project's Service Desk email.
This all works great so far. BUT, we need to get the issue-specific email address in order to provide an option for users to add a comment via this separate app. According to the documentation, the issue email address is readily available on the issue itself -- https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#copy-issue-email-address.
Is there a way to retrieve this issue-specific email via the GitLab API?
This information is available in the GET request of a project. The information on how to do this is on the API Documentation.
If the service_desk_enabled key is true, there will be an email address in the service_desk_address key. This will reflect the value in the settings of the project.
If you haven't changed any defaults, this looks like the email address is made up of:
"contact-project+"
project group name + "-"
project name + "-"
Project ID + "-"
"issue-#incoming.gitlab.com"
That way, if it's not available in the request but the setting is enabled, you should be able to build it
Related
I have 2 queries based on the following :
I recently followed this DocuSign article to pass a supplied document to Docusign via the API:
https://www.docusign.com.au/blog/get-the-flow-sending-docusign-envelopes-microsoft-power-automate?_ga=2.99447774.1174083755.1646148960-1179341585.1645460870
Query 1 - This all works apart from the AutoPlace text just isn't getting picked up. I added the variables as described in the article and referenced them in the document footer. The document is passed through the API call and the invitation to sign goes out ok. Is there anything I'm missing here? I can open the document for signing but docusign doesn't go to the places where the AutoPlace tags are, just leaves it open for the user to decide what to do. I've previously tried using AutoPlace using templates, but this is a document that will be sent through the API as it is provided by our users (with the correct AutoPlace intact). The article hints this should just work.
Update : this is now working but need advice on text color
signing screenshot
Update : Showing white signature on black background
white signature
Query 2 - Once the user has signed the document using the above, I want to trigger a power automate flow off. There is a trigger for this but when I try to form the connection to DocuSign, there is only a login for the main account, not the developer account. So the account where I've made the account from isn't the one where I can fire off the triggers from. This makes it impossible to then fire a flow when it has been sent to the API and subsequently signed. Is there a way to use the trigger using the same account as the API account? If not it seems a bit crazy that I can start the process using the API but then can't fire flows from the result of the signings.
We have a company account ( I'm working on behalf of Transport for Wales) but was told there is no API support at all, which also sounds a bit bizarre. Hoping someone can help me!
Query 1 - there's an AutoPlace settings that determine the scope - document/envelope for AutoPlace. You may want to see if the issue happens also when you use the web app and not from API - if the same challenge - then you need to contact support to change this scope. If not, it may mean you're not setting your templateRole correctly. It must match the same one that was defined on the template (case sensitive).
Query 2 - no, the OTB connector is production only. For the developer account you will need to use a custom connector for any REST API, not the one provided for you.
I am trying to build a logic app to email results of a devops query on a regular basis. When I use the 'Get query results' block in logic apps, I am unable to authenticate with my primary email address. Instead Logic Apps keeps picking up my alias email address when I try to change connection. No sign in screen is displayed so I assume my credentials are cached somewhere.
Any ideas on how I can change the account I use to login with?
Update
Trying to add a new connector using 'add new'
No option to sign in. Defaults to .uk account rather than using .co.uk account that I am signed into through Azure.
Under API Connections you can find any connections the Logic App is using. Click a connection to be able to edit or delete it.
EDIT:
If you would like to use another email address instead of the current one, delete the connection and create a new one from the Logic Apps designer.
We are using the following steps to successfully create our app while in testing mode but we cannot go live because the template ID is not there for a standard account.
We create the template at demo.docusign.net
We get the template ID
Our app works perfectly using API
But a normal user (our client) will create a template using docusign.com ... which does not Display the template ID and therefore he cannot put it in the APP.
How can I resolve this?
You have a couple options. When editing a template, the first page (which shows all of the details of the template) displays the Template ID at the top left. They could copy and paste it.
Arguably the better user experience is to use the DocuSign API to get a list of the available template names/IDs and let your users select the appropriate template within your app.
If you are using this https://github.com/docusign/docusign-csharp-client sample and testing please make sure you create a sandbox environment on docusign as the above sample uses https://demo.docusign.net/restapi as the Api URL,create integrator key and create template in demo environment only.I experienced same error(invalid template id) when I created a template on real(not sandbox) environment and used the above sample having demo API URL in my application and later when I changed to demo template id( by clicking cursor on (i)) I got the desired result.
Thanks
Ravi
I uploaded a file DocuSign_EmailResources.xml to override the Master file and I do not my the changes. The documentation says that 'The ability to use the resource file option is not
normally enabled for an account; contact your Account Manager or DocuSign Support for more
information about enabling this option in your account'.
Before we update our production, we would like test on our demo account using SOAP API. I just want to add a link to the Email text. When I try this through the API, the link is disabled in the email as it is being formatted by the server side program.
Is there any setting that I am missing.
Thanks in advance.
If you can see (and access) the Resources tab when Editing a Brand Profile in the DocuSign web console, then this should mean that "the ability to use the resource file..." is indeed already enabled for your account.
The Email Resource file is quite lengthy, and is divided into various sections -- each section being the email template that's used for a specific type of email that DocuSign sends. So, for example, if you wanted to modify the contents of the "signing invitation" email that DocuSign sends to a recipient when it's their turn to sign, you'd modify contents within the Envelope Activation section of the Email Resource File. Changes applied to other sections of the resource file would not impact/affect the signing invitation email. If you haven't already done so, I'd suggest that you review the Email Resource File Guide (http://www.docusign.com/sites/default/files/DocuSign%20System%20Default%20Email%20Formats.pdf) to ensure that you've modified the correct section of the resource file for the type of email that you intend to effect.
Also, keep in mind that each Email Resource File applies to a specific (single) Brand. So, if you have multiple Brands within your account, make sure that you're modifying the Email Resource File for the Brand that's used for the Envelopes where you expect/want customized email content.
I have deployed Orchard on azure and enable Email Messaging module. Enabling says it enables successfully and asks for email settings. I provided it the mail server setting. Strange thing is, User setting does not show me the settings which are dependent on email messaging module (Contact us email address and public site name) and does not show me ("Lost your password") link . Also I have built a module which sends email. This module is not sending email.
Same orchard package works fine and also email on my dev server with same mail server settngs(gmail smtp settings.) But email is not working on azure.
What am i Missing ?
thanx
Just FYI for anyone else who visits this Question, I just got this working from Azure using the gmail SMTP server without any third party add-ons. I simply added the following SMTP details:
Then used the contact form to send an email to myself. The first email gives me an alert to my gmail account:
Hi Simon,
Someone recently tried to use an application to sign in to your Google Account - XXX#gmail.com.
We prevented the sign-in attempt in case this was a hijacker trying to access your account. Please review the details of the sign-in attempt:
Monday, April 8, 2013 9:33:46 PM UTC
IP Address: 65.52.168.70
Location: United States
...blah blah blah
If this was you, and you are having trouble accessing your account, complete the troubleshooting steps listed at http://support.google.com/mail?p=client_login
Following the link give you the option to allow an application to login with your credentials. Just follow the link in step 3 and then you have 10 minutes to send another email from your orchard site. The next test message I received without issue.
Got it. Windows Azure itself does not allow sending email neither it allows to use SMTP. WE have to use third party email service like PostMark,SendGrid etc
http://blogs.msdn.com/b/publicsector/archive/2011/10/14/sending-and-receiving-email-in-windows-azure.aspx
So, I'm just curious how does WordPress, installed on Windows Azure (gallery), able to send emails?
http://coffee2code.com/wp-plugins/configure-smtp/
There are still too many different suggestions on the subject so i thought i should write what I've found useful. Here's what i did to get it to work:
My SMTP settings:
Sender address: myname#gmail.com
Hostname: smtp#gmail.com
Port: 587 (25 will also do)
SSL Communications: Checked
Credentials: My Gmail address and my password
These settings should work on your local environment just fine. But on the cloud you may need to do the following:
As your Azure VM may be at some arbitrary location, Gmail marks the login attempts as suspicious and blocks them. If this is the case, you should see a mail informing you about this suspicious activity in your inbox. Just follow the instructions there and mark the login as trusted. It will remain that way until somehow your IP on the cloud changes (e.g. deleting your deployment slot). VM relocation shouldn't be an issue since the IP still remains the same. You may have to do this separately for your staging and production slots.
Lastly, I enabled full trust for my web role as shown here:
http://blogs.msdn.com/b/windowsazure/archive/2009/03/18/hosting-roles-under-net-full-trust.aspx
I hope this helps others having this problem.
Cheers
No more third-party with GitLab 15.5 (October 2022):
Deliver emails using Microsoft Graph API with client credentials flow
If you’ve enabled security defaults in Azure AD,
legacy authentication protocols for SMTP are blocked.
You can now configure your GitLab instance to deliver emails using
Microsoft Graph API
with OAuth 2.0 client credentials flow.
See Epic, Documentation and Merge Request.
The gitlab.rb would include:
gitlab_rails['microsoft_graph_mailer_enabled'] = true
# The unique identifier for the user. To use Microsoft Graph on behalf of the user.
gitlab_rails['microsoft_graph_mailer_user_id'] = "YOUR_USER_ID"
# The directory tenant the application plans to operate against, in GUID or domain-name format.
gitlab_rails['microsoft_graph_mailer_tenant'] = "YOUR_TENANT_ID"
# The application ID that's assigned to your app. You can find this information in the portal where you registered your app.
gitlab_rails['microsoft_graph_mailer_client_id'] = "YOUR_CLIENT_ID"
# The client secret that you generated for your app in the app registration portal.
gitlab_rails['microsoft_graph_mailer_client_secret'] = "YOUR_CLIENT_SECRET_ID"
gitlab_rails['microsoft_graph_mailer_azure_ad_endpoint'] = "https://login.microsoftonline.com"
gitlab_rails['microsoft_graph_mailer_graph_endpoint'] = "https://graph.microsoft.com"