Bluesky Social (Independent Publisher) #3706
Conversation
|
@microsoft-github-policy-service agree company="Dan Romano aka IDR, Inc. dba SWOLCAT" |
|
Hi Dan, I have a connector I’m working on too. Are you building more out or is this what you are going to submit (without the Proposal)? |
Hi Troy, I will be building out more. These three actions are just the start and will be expanding in the next few hours. To get this up and running, we only need three actions but there's a lot more than we can and will add, naturally. What do you think? |
|
I tend to build them all. Are you having any problems with the OAuth? |
|
Right now, I've got basic auth going with the app passwords and rooting around for OAuth...but not seeing where we can create a client and secret. Posted in the dev channel on Bluesky but no response yet (recent post). |
|
@krautrocker Dan, please remove changes to the BkkFutar connector, I am not yet planning to update its authentication ;) |
Damn, my mistake - will remove at once this evening. |
This reverts commit ea3bcd3.
- Updated readme file
- Removed endpoints temporarily, adding back tomorrow
- Modified endpoints in readme
|
Test operation validation below. Proof of life: 1.) Create session
2.) Get preferences
3.) List notifications
/**/ Flow will be ready later tonight or tomorrow once warnings and schemas are otherwise validate. All errors have been cleared via paconn validate. |
|
Working flow: Actions list (non-exhaustive):
1.) Create session
/**/ More tomorrow! |
- paconn validated, no errors.
|
Custom connector UI returns a "cannot validate schema" warning for about 19 endpoints and 14 definitions. Digging into this, this can be attributed to nested references ($ref). I can add the schema definition inline so the connector UI can parse and validate. This affects a small number of endpoints. It's a handful of endpoints referencing definitions so if we put them inline, this may settle this...though I'm not crazy about adding definitions inline. $ref is cleaner and more organized but I would like validation to be as clean as possible. The connector does indeed save in the UI, so this isn't a showstopper (at least not at the moment). |
|
Work remaining:
|
- Modified the ImportRepo endpoints based on paconn validation - paconn validated, no errors.
|
Setting up a PDS this weekend. Stay tuned @Laskewitz |
|
PDS setup complete. It is online and accessible via web front end. DNS is resolving, allowing at least a half hour. Next: 1.) We will connect to the instance via Power Automate Then: 2.) Create a flow to test session token creation and refresh, confirming joy on the authentication mechanism. From there: 3.) We will be in a position to test the rest of the endpoints with the connector. The testing schedule shall commence per namespace:
Human users have been engaged to help create lists, starter packs, send DMs, upload videos and memes, etc. Success criteria:
Target UAT completion date: January 19th |
- Validated with paconn, no errors. - Changed security definition to "api_key" from "bearerAuth"
|
Made quite a dent but a few things have tripped up the effort. 1.) TikTok still in play. We've been monitoring the situation around social media platforms closely over the past few weeks. TikTok has gone dark officially but we expect it to return based on comments from the incoming administration. Palace intrigue indeed, and the situation remains fluid. 2.) Testing is 25% complete. I would like to post figures to show testing progress, which is currently at 25%. Figures below the following comments:
A few discussions in forums says this goes away on its own but something else is going on here.
apiProperties will be updated to handle dynamic hosts: Host: {{host}} Hosts will change dynamically at runtime; a particular flow construction must be used. When calling endpoints that don't use the bsky.social default endpoint, a flow needs to change the host to, say, the chat service, api.bsky.chat. /**/
More tomorrow and the rest of this week. |
|
Hello @krautrocker, Is it ready for review? if not, we would request you to close this PR and submit when the connector is ready |
|
@vmanoharas I'm actively working on it. Parts of it are ready and I'm updating the PR as I go along. What's the policy here? |
|
@vmanoharas Wouldn't it be better for Dan just to restore the [Proposal] tag to the PR title? There's no reason to disconnect his existing commits |
|
Again, what's the policy? |
…hing host for different endpoints
|
@vmanoharas All set for now. Please proceed. |
- Validated with paconn, no errors.
There was a problem hiding this comment.
Dear Partner
I hope you are doing well.
Congratulations, your pull request is approved. We will move forward with the certification process. We are preparing your connector for production deployment and will queue up for the next deployment schedule. Once your connector onboards the next deployment schedule, it starts to deploy your connector in our production environments that typically takes 4-5 weeks.
Please let us know if you have any questions.
Thank you very much for working with us.
|
[[certify-connector]] |
|
[heart] Daniel Laskewitz reacted to your message:
…________________________________
From: vmanoharas ***@***.***>
Sent: Wednesday, January 29, 2025 3:54:28 PM
To: microsoft/PowerPlatformConnectors ***@***.***>
Cc: Daniel Laskewitz ***@***.***>; Mention ***@***.***>
Subject: Re: [microsoft/PowerPlatformConnectors] Bluesky Social (Independent Publisher) (PR #3706)
@vmanoharas approved this pull request.
Dear Partner
I hope you are doing well.
Congratulations, your pull request is approved. We will move forward with the certification process. We are preparing your connector for production deployment and will queue up for the next deployment schedule. Once your connector onboards the next deployment schedule, it starts to deploy your connector in our production environments that typically takes 4-5 weeks.
Please let us know if you have any questions.
Thank you very much for working with us.
—
Reply to this email directly, view it on GitHub<#3706 (review)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA4XUO6DBHI3JGU4WOOZYOT2ND2TJAVCNFSM6AAAAABRQQQTVKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDKOBRGQ4TIOJYGE>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Hi Dan,
Please correct me if I'm wrong with reference sources. I've also reached out to Lane Swenka to see if these policies are in development. @vmanoharas did the apiProperties fail your validator? |
…tandard). Updated x-ms-apimTemplateParameter.host to x-ms-apimTemplateParameter.urlTemplate.
- Removed acquiretoken (not a valid template).
- identifier now used instead of username in authentication.
- runPolicyOn removed; replaced with x-ms-apimTemplate-policySection: Request.
- accessJwt moved to connection parameters.
- accessJwt now stored as a secure connection parameter.
- Updated setheader policy: Authorization: Bearer {{accessJwt}}
|
Hi Dan, |
|
I see, I misunderstood you there. Let me take another look. Thanks, @troystaylor |
…ntication instead of headers. - Added C# script to integrate with apiProperties authentication. - paconn validated, no errors.
|
Alrighty, took a sec but let's see how this tests out. Stay tuned and thank you! |
| _logger.LogError("404 Not Found: The requested resource does not exist."); | ||
| return BuildErrorResponse(HttpStatusCode.NotFound, "The requested resource was not found."); | ||
|
|
||
| case (HttpStatusCode)529: |
There was a problem hiding this comment.
@krautrocker, maybe this should be HTTP status code 429, to align with Rate Limits
| Bluesky / 429 Too Many Requests - HTTP | MDN?
When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.
apiDefinition.swagger.json, by runningpaconn validatecommand.apiProperties.jsonhas a valid brand color and doesn't use an invalid brand color,#007ee5or#ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process: