Author: Jared Meredith

azure, HTML, Web

Step-by-Step Guide to Deploy Azure Static Web Apps

Jared Meredith

Enjoy this post of me bringing myself back into some of the basics to better help me keep my solutions architecture reflex fresh (ha)!

Use Case: I need a static page to host a logout page when users leave the SSO experience to land them to a custom-tailored page where I can provide the right guidance and support language related to the app.

So, where to begin?

First, here are some prerequisites to success:

Next, let’s pull down from a basic starter code kit to save some time on creating it from scratch:

https://github.com/new?template_name=vanilla-basic&template_owner=staticwebdev

And boom, just like that a repo with stuff:

But what to do now? Well so far we now have code, but still need a destination and a means to deploy it.

For a destination let’s go onward to Azure:

  • Go to the Azure portal and sign-in
  • Select Create a Resource.
  • Search for Static Web Apps.
  • Select Static Web Apps.
  • Select Create.

In the Basics section, begin by configuring your new app and linking it to a GitHub repository.

SettingValue
SubscriptionSelect your Azure subscription.
Resource GroupSelect the Create new link, and enter rg-static-app-deploy in the textbox.
NameEnter static-app-deploy in the textbox.
Plan typeSelect Free.
SourceSelect GitHub and sign in to GitHub if necessary.

If necessary, sign in with GitHub, and enter the following repository information.

SettingValue
OrganizationSelect (your organization).
RepositorySelect (your repo name).
BranchSelect (your branch e.g. main).

Once you have completed the wizard then you should see a successful creation of your resource to deploy to. (there are CLI references for those who prefer that below).

Your URL from the vanilla template should be live!

Within Github you can inspect the yaml that drove the deployment action (depending on what you pick for your token and deployment configuration this will vary):

You can also see where the secret is managed within Settings > Secrets and Variables > Actions:

Some extra credit -> want to add a custom domain to it?

Additional extra credit -> you can also have the app be front-ended with Azure Front Door.

Finally, if you’re not going to continue to use this application, you can delete the Azure Static Web Apps instance through the following steps:

  1. Open the Azure portal.
  2. Search for static-app-deploy from the top search bar.
  3. Select the app name.
  4. Select Delete.
  5. Select Yes to confirm the delete action (this action may take a few moments to complete).

References:

EA

Optimizing Enterprise Architecture Initiatives: Partnering Model and Essential Stages

Jared Meredith

In the ever-evolving landscape of enterprise architecture, the journey from discovery to implementation is a complex yet rewarding process. Through this process there are critical phases of this journey, with every portion focused in how you partner with your teams. Join me as we navigate through these essential stages, offering insights and best practices to ensure your enterprise architecture initiatives thrive.

The Discovery Phase is crucial for understanding the key people involved, their goals, and the challenges ahead. This phase involves identifying strategic priorities to support business outcomes and envisioning the ideal future state without limitations. It also includes planning timelines, understanding deliverables, and ensuring that teams are well-coordinated. By addressing these aspects, we can proactively evaluate and review our progress, tailoring our vision to meet reality while supporting ongoing needs.

During the Initial Architecture Reviews, the focus shifts to designing and presenting the architecture. This involves documenting the current state, defining technical requirements for the future state, and accounting for any third-party dependencies. The design must comply with architectural standards and be pre-aligned with build teams. Once the design is ready, it is presented to the architecture review board and stored for long-term use. The iterative review process includes listening to feedback, learning from ongoing changes, and improving processes to accelerate compliant development. This ensures that documentation and education are effectively conveyed to support teams and stakeholders.

Last but not least, the Iterative Architecture Reviews emphasizes continuous improvement and adaptation. It involves regularly assessing how well the processes are working and identifying areas for enhancement. By staying informed about ongoing movements and changes, teams can plan ahead and allocate time for understanding new upcoming work. This phase also focuses on conveying documentation and education effectively, ensuring that everyone involved is well-informed and capable of contributing to the enterprise architecture’s success.

Let’s now take a deeper dive in how the partnering model comes together with each of these phases:

Enterprise Architecture Partnering Model

As seen above the partnering model doesn’t end once an architecture is drawn; if anything it only continues to iterate over time. To show this better, here’s a full breakdown of each phase of the partnering model with key questions that should be understood at each part:

Understanding (Part of Discovery)​

  • Who are the key people to work with? ​
  • What are their goals? their team goals? ​
  • What are the challenges ahead? ​
  • What do we not know yet that will help us understand? ​
  • How can we help support the ongoing needs? ​

Visioning (Part of Discovery)​

  • What are the strategic priorities to support business outcomes? ​
  • What is the north star? What is the ideal future state with no limitations? ​
  • How are we aiming towards the dream state over 1 year? 3 years? 5 years? ​
  • What can we do to be proactive in evaluation and review? ​
  • How can we tailor the dream to meet reality? ​

Planning (Part of Discovery)​

  • Do we have a timeline and understanding of the deliverables? ​
  • When and how are the teams meeting? ​
  • How can we get plugged into the ongoing conversations? ​
  • Have we planned enough time to evaluate and design the architecture? ​
  • Who is involved to help manage the gates through the project lifecycle? ​

Designing (Part of Initial Architecture Reviews)​

  • Do we have an understood and documented current state? ​
  • Do we have technical requirements to support the future state? ​
  • Are there 3rd party external dependencies to account for? ​
  • Does the design accommodate to architectural design standards?​
  • Have the designs be pre-aligned with build teams prior to architecture review? ​

Presenting (Part of Initial Architecture Reviews)​

  • Does the diagram comply with architectural design standards? ​
  • Has the diagram been presented to architecture review board? ​
  • Has the diagram been stored for long-term use with support teams? ​
  • Has the status of the review been communicated to the project/program teams? ​
  • Have we validated the design with any 3rd party external support? ​

Listening (Part of Iterative Architecture Reviews and Discovery)​

  • How are we doing? What can be shared about what could be better? ​
  • Where can we learn of ongoing movement or changes? ​
  • How can we improve any processes or standards to accelerate compliant development? ​
  • How can we plan ahead to make time for building understanding of new upcoming work? ​
  • How are we conveying documentation and education to others that they may learn more about EA? ​

As you work to develop your EA partnerships I know that you’ll see these themes as you go along. I hope this has been helpful, happy architecting!

Web

Remember the 5-9, not just the 9-5!

Jared Meredith

Me: (Joins a conference call)

Someone on call: “Hey, how are you?”

Me: “Good”

Also Me: (pondering if I just lied or not)

What did “Good” mean for that day?

Let’s review the last 24hr:

12:05 – 12:30 AM – kid diaper change, make a bottle, feed, rock, back in bed

12:30 – 4 AM – sleep

4:05 – 4:30 AM – kid diaper change, make a bottle, feed, rock, back in bed

4:30 – 7 AM – sleep

7:05 – 7:30 AM – kid diaper change, make a bottle, feed, playtime, handoff to help

7:30-7:50 AM – shower and change

7:50 – 8:30 AM – morning commute, catching up with friends and family

8:30 – 9 AM – meeting

9 – 10 AM – meeting

10 – 11 AM – meeting

11 – 11:30 AM – snack & break, catch up with kiddo

11:30 – 12 PM – meeting

12 – 12:30 PM – meeting

12:30 – 1 PM – break, catch up on emails and chats that haven’t been hit yet

1 – 2 PM – meeting

2 – 3 PM – meeting + (call during the meeting to check in on kiddo and plans for the evening)

3 – 4 PM – meeting (commuting home)

4 – 4:30 PM – meeting

4:30 – 5 PM – kid diaper change, make a bottle, feed, play, back in bed

5 – 6 PM – dinner, discussing tomorrow’s plans

6:30 – 7:30ish PM – diaper change, bath time, make a bottle, feed, play, back in bed

7:30ish – 10 PM – finish last touches on work, spend time decompressing

10 PM – 12 AM – trying to fall asleep 

After I thought about it, I probably could have said “tired” and ranted about it…but I also know folks are just trying to be nice.

All that to say, please be mindful of people’s 5-9. You never know what kind of schedule is happening outside 9-5.

Next time you ask someone how they are, remember that “Good” might have a lot more behind it.

Also remember that stress may be on people, even in their replies or tone. We must do our best to lead with empathy and understanding as much as we can accommodate. The more we do, the more I feel like people will return it in kind.

That’s all for now, carry on.

#worklifebalance #5to9 #mindfulness #newparent

Web

Presentation Now Available: The Power of Cross-Platform Automated Web-Based Testing in CICD Pipelines

Jared Meredith

Thanks again TESTINGMIND for the chance to speak and present – great job to the other presenters as well, learned a lot.

My presentation is now available here

#qaautomation #qa #qatesting #testingmind

View the session information from #TAS20 here: https://www.linkedin.com/posts/testingmind-consulting-pvt%2E-ltd%2E_last-week-we-completed-a-rally-of-software-activity-6722944641982971904-dxSD

Blog

TLDR: Reflection + Pain = Progress

Jared Meredith

Reflection:

Been presenting ideas lately and having some tough conversations as of late and feeling pretty defeated from it…BUT I am however reminded that the improvement does not come without a certain degree of failure.

Pain:

Without a healthy cycle of debate to review your goals and decisions it is tough to see if your plans and ideas can stand against criticism or not. It may very well turn your plans upside down.

Progress:

As you gain clarity and discuss with your colleagues and partners, things begin to improve in the vision and strategy to execute.

So, if from time to time you also feel defeated from conversations, be reminded of this equation and its impact in your every day.

#learning #goals #growth #principles #raydalio